Enhanced network congestion application programming interface

ABSTRACT

Reception of network load data is disclosed. For instance, the network load data can provide indication of a utilization level extant in a wireless cellular network. The systems and methods, as a function of the utilization level, determine a congestion metric that indicates a level of congestion determined to have been experienced by a communication packet using the wireless cellular network device. Further, the disclosed systems and methods schedules transmission of communication packets to an end user device via the wireless cellular network device, as a function of the determined congestion metric.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 16/289,858, filed Mar. 1,2019, and entitled “ENHANCED NETWORK CONGESTION APPLICATION PROGRAMMINGINTERFACE,” which is a continuation of U.S. patent application Ser. No.14/534,499 (now U.S. Pat. No. 10,225,761), filed Nov. 6, 2014, andentitled “ENHANCED NETWORK CONGESTION APPLICATION PROGRAMMINGINTERFACE,” the entireties of which applications are hereby expresslyincorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to the provision of networkfunctionality metrics via network application programming interfaces(APIs) to invoking applications.

BACKGROUND

Delivery of multimedia content from/between/to mobile wireless cellularendpoint devices and/or server devices has become prevalent in thepresent age. One issue that can affect user experience in regard toreceiving and/or transmitting multimedia content over a mobile cellularnetwork in a continuous stream of network communication packets can benetwork congestion associated with the mobile cellular network. Suchnetwork congestion and/or overutilization can cause streams of networkcommunication packets transmitted from first endpoint devices to bedelayed, causing what should be a seamless and/or ordered stream ofnetwork communication packets to be received at receiving endpointdevices as discontinuous and/or disordered packet streams causingquality of service issues and consequently end user dissatisfaction.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system for scheduling transmission ofstreams of transmission packets between/from/to various devices inaccordance with aspects of the subject disclosure.

FIG. 2 is a further depiction of a system for transmitting consecutive,continuous, and/or uninterrupted streams of network communicationpackets between network endpoint devices, in accordance with aspects ofthe subject disclosure.

FIG. 3 illustrates a further system for transmitting or schedulingtransmissions of consecutive network communication packets in acontinuous uninterrupted stream from a server end point device to aplurality of client end point devices in accordance with aspects of thesubject disclosure.

FIG. 4 is still yet an additional illustration of system fortransmitting and/or scheduling transmission of network communicationpackets in a continuous, uninterrupted, and/or consecutive seriesbetween mobile wireless cellular endpoint network devices in accordancewith aspects of the subject disclosure.

FIGS. 5A and 5B provide representation of a mean network utilizationthat can be encountered or experienced in a typical mobile wirelesscellular network in accordance with aspects of the subject disclosure.

FIG. 6 provides illustration of a flow chart or method for schedulingtransmission of streams of transmission packets from a server device toan end user device or user equipment device in accordance with aspectsof the subject disclosure.

FIG. 7 provides another illustration of a flow chart or method forscheduling transmissions of consecutive transmission packets in acontinuous uninterrupted stream from a server device to an end userdevice or user equipment device in accordance with aspects of thesubject disclosure.

FIG. 8 illustrates another flow chart or method for schedulingtransmission of communication packets in an uninterrupted, continuous,and/or consecutive stream between two or more endpoint network devicesin accordance with aspects of the subject disclosure.

FIG. 9 is a block diagram of an example embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

One category of application programming interfaces (APIs) are networkinformational APIs that provide calling/invoking applications withnetwork related information that can cause and/or facilitate thecalling/invoking application to adjust or change their servicebehavior(s) to achieve the best possible user experience forend-user(s). One such API can be a network load API, sometimes referredto as a congestion API, which in the context of mobile wirelessnetworks, typically can provide indication of network conditions relatedto cell/sector load/utilization, and based at least in part on theseindications, a calling/invoking application can in one instance, forexample, dynamically and/or automatically change (e.g., reduce orenlarge) the size of transmitted content (e.g., by modifying the size ofthe entire file) scheduled to be transmitted over the wireless cellularnetwork depending on whether or not the network load API has indicatedthat the wireless cellular network is experiencing a high level ofcongestion.

For example, if the wireless cellular network (or a cell/sector thereof)has entered a high load/congestion state, the network load API canprovide indication to an calling application (e.g., an application thatplaces a premium on the real-time service of communication packets, suchas a video streaming server application) that network congestion levelsare such that the calling application should, as a function of theindicated high congestion state, reduce the size of the transmittedcontent (e.g., by transcoding (or re-transcoding) the content based oncongestion state) employed to transmit the video stream to a videostreaming client operational on an end user device (e.g., smart phones,tablet computers, laptop computers, notebook computers, desktopcomputers, server class computing devices with or without wired and/orwireless capabilities, electronic devices inclusive of processors and/ormemories, consumer and/or commercial wired/wireless devices, industrialwired and/or wireless equipment, avionics components, and the like).Such reductions in the size of transcoded (or re-transcoded) and/ortransmitted content in the context of the foregoing example can ensurethat the video stream is provided to the end user device in a timelyfashion thereby ensuring that end user expectations are notdeleteriously affected. In a similar vein and in continuation of theforegoing example, when network congestion is low or negligible thenetwork load API can provide indication to an invoking process (e.g.,video streaming server application) that network congestion is currentlylow and that the invoking process could possibly increase the overallsize of the content utilized to fulfill video streaming requestsemanating from the video streaming client operational on the end-userdevice.

Additionally and/or alternatively, and once again in the context of theforegoing illustration, when a video streaming server application isprovided indication by a network load API that network congestion is ina high load/congestion state, the video streaming server applicationcan, for instance, reduce the resolution with which the streamingcontent is delivered and/or reduce the picture size of the video contentthat will be delivered to the video streaming client executing on theend-user device. Thus, while an end user may experience marginallydegraded picture quality and/or smaller picture sizes associated withthe video stream, the continuity of the video stream can be preservedand all communication packets within which the video stream is includedcan be assured of timely delivery to the end-user device and subsequentdisplay by the video stream client.

As will be appreciated by those of ordinary skill, the foregoing examplepertains to situations where communication exchanges need to be in realtime or in near contemporaneity. In instances where communicationexchanges do not need to be in real time, invoking applications, basedat least on, or as a function of, indications from a network load APIcan delay their transactions; this is sometimes referred to as “timeshifting”.

A load indication as generated by a network load/congestion API istypically an average utilization/load level reported over a definedperiod of time. The classic network load indicator API provides anindication in terms of some load or utilization level. This utilizationlevel can be represented, for example, as a numeric value on a scale of0-100%, or as a mnemonic such as High, Medium, Low.

In the context of a network load/congestion API, a load indicator isexpected to be used just prior to a communication, so a load indicationprovided by a network load/congestion API would be most useful if itwere to include a prediction related to the expected congestion that acommunication packet transmitted between two communication end-pointnetwork devices could potentially encounter in a defined or determinableprospective period of time. To date, most network load/congestion APIshave been backward looking, concerned mainly with past events; concernedwith how congested a wireless communication network was in the (recentand/or distant) past.

Generally, a mobile wireless cellular network (or more specifically theair interface of the mobile wireless cellular network) can be expectedto show frequent varying load conditions. Some of these load conditionscan be so high that they can lead to congestion in the network. Whenthese periods of high load conditions or congestion are short and/or aresufficiently intermittent, most reliant applications have sufficientonboard protocols/processes to provide the elasticity to ameliorate suchcongestion events and to ensure a satisfactory service experience forend users. However, when periods of high load conditions or congestionbecome significantly longer, the onboard ameliorative protocols canbecome ineffective which can result in end-users experiencing, at best,slower reaction times and a diminished service experience. For manyapplications that are not reliant on transmission of time critical (realtime) communication packets over the mobile wireless cellular network,long durations of network congestion can be inconsequential and not ofvital importance. Applications, such as streaming applications (e.g.,applications that rely on the transmission of a continuous stream ofcontent included in transmitted communication packets, such as videostreaming applications), that can be dependent on the real time, or nearcontemporaneous, ordered or sequential delivery of transmitted contentcontaining communication packets can be particularly susceptible tovarying and long duration network congestion. Applications of the lattersort could certainly benefit from knowing more than the average networkutilization currently extant in the mobile wireless cellular network, inparticular, such applications could benefit from knowing in real timethe network utilization for an entire prospective duration in which astream of content is to be transmitted in a continuous stream oftransmission packets to an end user device, be that defined or definableprospective duration merely last 6 seconds for a brief video clip, theduration for the playing of a feature length film, or the entirebroadcast of a sporting event. Nevertheless, in these situations it willbe appreciated that longer communications of longer durations willtypically encounter more varying and disparate load levels.

In accordance with the foregoing, the subject disclosure describes anetwork load API or a congestion API that includes an indication as towhether an observed and reported utilization interval has a plethora oflong duration congestion events. As has been observed, long durationcongestion events are currently not reported by network load/congestionAPIs. Indicators that provide identification as to whether or not aplurality of long duration congestion events within a defined ordefinable time period have occurred can be beneficial for applicationsthat need to stream content in continuous streams of successivetransmission packets to an end user device. Such indicators can permitthese applications to better cope with the disruptive effects longperiod congestion events can have on streams of transmission packetstransmitted, from a server device to an end user device, that need to bereceived by the end user device in an ordered succession (e.g., thefirst packet transmitted by the server device to the end user deviceneeds to be received by the end user device first (or in nearcontemporaneity to the beginning of the directed stream of packets) andthe last packet transmitted by the server device to the end user deviceneeds to be received by the end user device last (or in nearcontemporaneity to the end of directed the stream of packets).

In order to facilitate the foregoing the subject disclosure disclosesand describes a system, apparatus, or device comprising: a processor,and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations. The operations cancomprise receiving network load data that indicates, as a first functionof a wireless cellular device, a usage level, or output, of the wirelesscellular network device over a defined duration of time; as a secondfunction of the usage level, determining congestion data representing acongestion metric that indicates a level of congestion determined to beexperienced by a first communication packet using the wireless cellularnetwork device; and scheduling transmission of a second communicationpacket to an end user device via the wireless cellular network device,as a third function of the congestion data.

Additional operations that can be performed by the system, apparatus, ordevice can also include: determining, as a function of the congestiondata, stability data representing a stability factor used for schedulingtransmission of the second communication packet; and determining thestability data as a function of determining a clustering of thecongestion data around an estimator, wherein the estimator is a meanlevel of congestion, a median level of congestion, or a modal level ofcongestion.

Further operations performed by the system, device, or apparatus canalso include: determining the stability data as a function ofdetermining a variance of the clustering of congestion data around theestimator; determining the stability data as a function of determiningan average deviation of the clustering of congestion data from theestimator; determining the stability data as a function of determining amean absolute deviation of the clustering of congestion data from theestimator; determining a skewness of a distribution of the congestiondata from the estimator; and determining a kurtosis of a distribution ofthe congestion data in relation to the estimator.

Other additional operations that can be performed by the describedsystem, device, or apparatus can comprise determining, as a function ofthe congestion data and the stability data, prediction data representinga prediction for a prospective defined period of time regarding thelevel of congestion that is to be experienced by the wireless cellularnetwork device as a result of transmitting the second communicationpacket; and determining the level of congestion as a function ofenumerating, from the network load data, a first number of congestionevents that exceed a first threshold value, wherein the first thresholdvalue is a defined utilization level.

Additional operations performed can include determining the level ofcongestion as a function of further enumerating, from the first numberof congestion events that exceed the first threshold, a second number ofcongestion events that surpass a second threshold value, wherein thesecond threshold value is a defined time period over which a congestionevent in the first number of congestion events exceeds the firstthreshold.

In accordance with a further embodiment, the subject disclosuredescribes a method, comprising a series of acts that can includereceiving network load data that indicates, as a first function of anetwork device, a usage level of the network device over a definedduration of time, wherein the network load data represents cellutilization condition data received from one or more of an operationsupport system device, a mobile switching center device, a network probedevice, a base station controller device, a base transceiver device, ora data storage device; as a second function of the usage level,determining congestion data representing a congestion metric thatindicates a level of congestion determined to be experienced by a firstcommunication packet using the network device, wherein the congestionmetric is determined as a function of enumerating a number of congestionevents that exceed a threshold value; and transmitting a secondcommunication packet to an end user device via the network device, as athird function of the congestion data.

Additional acts can include using stability data representing astability factor to transmit the second communication packet; usingprediction data representing a prediction for a future defined period oftime regarding the level of congestion that is to be experienced by thenetwork device as a result of transmitting the second communicationpacket.

In accordance with a still further embodiment, the subject disclosuredescribes a computer readable storage device comprising instructionsthat, in response to execution, cause a computing system comprising aprocessor to perform operations. The operations can include receivingcell sector load data that indicates, as a function of a device, a usagelevel of the device over a defined duration of time; as a function ofthe cell sector load data, determining congestion data representing acongestion metric that indicates a level of congestion determined tohave been experienced by a first communication packet using the device;and transmitting a second communication packet to an end user device viathe device, as a function of the congestion data.

Now with reference to the Figures. FIG. 1 illustrates a system 100 forscheduling transmission of streams of transmission packets from a serverdevice to an end user device or user equipment device. System 100 caninclude detection engine 102 that can be communicatively coupled toprocessor 104, memory 106, and storage 108. Detection engine 102 can bein communication with processor 104 for facilitating operation ofcomputer or machine executable instructions and/or components bydetection engine 102, memory 106 for storing data and/or the computer ormachine executable instructions and/or components, and storage 108 forproviding longer term storage of data and/or machine and/or computerexecutable instructions. Additionally, system 100 can also receive input110 for use, manipulation, and/or transformation by detection engine 102to produce one or more useful, concrete, and tangible result and/ortransform one or more articles to different states or things. Further,system 100 can also generate and output the useful, concrete, andtangible result and/or the transformed one or more articles produced bydetection engine 102 as output 112.

As will have been observed from the foregoing, system 100 can be anytype of mechanism, machine, device, facility, and/or instrument thatincludes a processor and/or is capable of effective and/or operativecommunications with a network topology. Mechanisms, machines, devices,facilities, and/or instruments that can comprise system 100 can includetablet computing devices, handheld devices, server class computingmachines and/or databases, laptop computers, notebook computers, desktopcomputers, cell phones, smart phones, consumer appliances and/orinstrumentation, industrial devices and/or components, hand-helddevices, personal digital assistants, multimedia Internet enabledphones, multimedia players, and the like.

Detection engine 102 in collaboration with processor 104, memory 106,and/or storage 108 can receive, as input 110, load data comprisingcell/sector load/utilization conditions from, for example, mobilewireless cellular network devices that can comprise one or more ofoperations support system devices, mobile switching center devices, basestation controller devices, base transceiver station devices, networkprobe devices, and/or one or more remote and/or local databases or datastores persisted to database server device(s). In response to receipt ofload data, detection engine 102, as a function of, or based on, the loaddata can determine a level of congestion currently extant in the mobilewireless cellular network, thereby providing a congestion metric. Thelevel of congestion can be measured, for instance, by observing that aquantum of congestion events exceed a first defined or predeterminedthreshold or first set point value, such as a mean utilization thresholdvalue, and that the observed quantum of congestion events surpass asecond defined or definable threshold value or second set point related,for example, to a period or duration of time, such as one millisecond,one second, one minute, etc. over which each of the observed quantum ofcongestion events extend. In this manner, long (and/or excessively long)duration congestion events that surpass, for example a mean, modal,and/or median utilization, can be noted, and such observations canthereafter be beneficially utilized by invoking or calling applicationsto schedule packet transmissions that can involve the transmission ofcontinuous series or successive sequences of packets containing contentthat is required to be received by an end user device, for example, asan uninterrupted continuous sequence of consecutive communicationpackets. It should be noted in this regard that calling or invokingapplications, such as video streaming applications, can have to transmitsignificant magnitudes of consecutive transmission packets overprolonged durations of time.

Thus, in response to, based on, or as a function of, the determinedmetric regarding the level of congestion, or more specifically, thequantum of long duration congestion events that have exceeded orsurpassed a fixed or established utilization threshold value and/or thatextend beyond a predetermined, identified, or distinct time period ortime horizon assessed to have occurred in the mobile wireless cellularnetwork, an application, such as a streaming application, utilizing thedisclosed and described network load API can schedule transmission ofpackets in order to avoid or obviate long duration congestion events.

Detection engine 102, based on, as a function of, or in response to,determining the measured level of congestion metric associated with amobile wireless cellular network (e.g., an observation regarding anumber of network traffic occurrences that both transcend an establishedor defined threshold value pertaining to a mean, median, and/or modalmobile wireless cellular network utilization and/or that surpass a setpoint related to a defined duration of time over which each of thenetwork traffic instances occurred) can determine a stability factorassociated with the measured level of congestion metric. The stabilityfactor can be determined by using one or more statistical methodologiesto ascertain how stable the level of congestion within the mobilewireless cellular network has been in the immediate past. Suchstatistical methodologies can include, for example, determining whetheror not there is a perceptible central clustering of the distribution ofmeasured level of congestion around an estimator, such as a mean,median, or mode and thereafter determining the variability of thedistribution of measured levels of congestion around the estimator. Forinstance, in order to determine the variability of the distributionaround the estimator, variance and/or standard distribution analyses canbe carried out.

Additional and/or alternative techniques that can be carried out bydetection engine 102 to determine the centrality of the distribution ofmeasured levels of congestion around the estimator can also includedetermining average deviations from the estimator, mean absolutedeviations from the estimator, skewness of the distribution in relationto the center of the distribution, and/or the kurtosis of thedistribution of measured levels of congestion (e.g., the relativepeakedness or flatness of the distribution relative to the estimator).

Thereafter, as a function of, and/or based on, the stability factordetermined by detection engine 102 and disseminated as output 112, aninvoking or calling application utilizing the stability factorassociated with the measured level of congestion metric (and/or inconjunction with the measured level of congestion metric) can transmitcontinuous uninterrupted steams of communication packets to end userdevices and/or user equipment devices while avoiding any long durationcongestion events that can be prevalent within the mobile wirelesscellular network.

Additionally, detection engine 102, as a function of load data relatedto cell/sector load/utilization condition data received from mobilewireless cellular network devices that can include, operations supportsystem devices, mobile switching center devices, network probe devices,base station controller devices, base transceiver devices, and/ordatabases stored in or on remote and/or local database devices ordatabase storage devices, can determine a level of network congestioncurrently extant between the two or more endpoint network devices. Thelevel of network congestion extant between the two or more endpointnetwork devices can be evaluated based on, or as a function of, anenumeration of congestion events that can have occurred during a definedor identifiable duration of time (e.g., nanosecond, millisecond, second,minute, quarter hour, half hour, one hour, between two defined and/ordeterminable points in time, etc.) that exceed a first threshold valueor first set point that relates to a mean, median, and/or modal mobilewireless cellular network utilization and/or that surpasses a secondthreshold value or second set point that pertains to the duration orlength of the each congestion event within the defined or identifiableduration of time. Based on, or as a function of, the level of networkcongestion, detection engine 102 can assess a stability factorassociated with the level of network congestion. As noted earlier, thestability factor associated with the level of network congestion extantbetween the two or more endpoint network device can be obtained by usingstatistical methodologies, such as determining whether or not there isan observable clustering of the distribution of congestion events aroundan estimator, such as a mean, median, or modal congestion event, and/orthereafter determining a variance in relation to the distribution ofcongestion events from the mean, median, or modal congestion event.Additional and/or alternative non-limiting statistical techniques thatcan also be beneficially utilized in this regard can include: obtainingan average deviation from the estimator, identifying a mean absolutedeviation from the estimator, evaluating skewness of the distribution inrelation to the estimator, and/or assessing a kurtosis associated withthe distribution of congestion events relative to the estimator.

Detection engine 102 can also supply a prediction related to thestability factor, wherein the prediction regarding the stability factorcan be associated with the stability factor. In this regard, theprediction supplied by detection engine 102 provides an indication as towhether or not the congestion or the non-congestion and/or the level ofcongestion or level of non-congestion is expected to last into aprospective defined or determinable near future time period. Onetechnique that can be used by detection engine 102 for assigning orassociating a prediction regarding the stability factor associated withthe level of congestion can include employing a probabilistic based orstatistical based approach, for example, in connection with making aninference related to the stability factor associated with the level ofcongestion. In this instance, inferences can be based in part uponexplicit training of classifiers or implicit training based upon systemfeedback, previously persisted metrics associated with congestion levels(e.g., supplied or obtained from operation support system devices,mobile switching center devices, network probe devices, base stationcontroller devices, base transceiver station devices, one or moredatabases and/or data stores persisted to remote and/or local datastorage devices, and the like). Any suitable scheme (e.g., neuralnetworks, expert systems, Bayesian belief networks, support vectormachines (SVMs), Hidden Markov Models (HMMs), fuzzy logic, data fusion,etc.) can be used by detection engine 102 to provide an appropriateprediction to associate with the stability factor. Historical dataand/or extrinsic data, for example, can beneficially be used bydetection engine 102 to compute a cost of making an incorrectdetermination or inference versus a benefit of making a correctdetermination or inference. Accordingly, a utility-based analysis can beemployed to provide a prediction in relation to the stability factor.Ranking and confidence measures can also be determined and employed inconnection with such a predictive analysis.

It should be noted in connection with the foregoing, that while therelationship between detection engine 102 and invoking applications hasbeen described in context of a “pull” mechanism (e.g., applicationsrequest detection engine 102 to supply metrics, individually and/or incombination, related to levels of extant congestion, stability factorsassociated with levels of congestion, and/or predictions related tocongestion and/or stability or instability assessments into theprospective future), the subject disclosure is not so limited, as “push”mechanisms for disseminating observed congestion levels, stabilityfactors associated with the congestion levels, and/or predictionsrelated to the congestion levels and/or determined stability factors canbe facilitated and/or effectuated by detection engine 102.

In accordance with a “push” mechanism, the mechanism can be initiated,for example, by an application requesting detection engine 102 to supplymetrics related to extant network congestion, stability factors relatedto the network congestion, and/or predications related to predictedfuture congestion levels and/or stability factors associated withpredicted future congestion levels. Additionally and/or alternatively,the “push” mechanism can be initiated when an application requestsdetection engine 102 to supply one of the extant network congestion, thestability factors related to the network congestion, or predictionsrelated to predicted future congestion levels and/or stability factorsassociated with the predicted future congestion levels. Once the supplyof congestion metrics has been initiated, detection engine 102 candeliver (e.g., push) congestion metrics on a periodic and/or on a randombasis for as long as is required.

Typically, requests for congestion metrics under the ‘pull’ mechanism toinitiate dissemination of congestion metrics are independent fromcommunication requests initiating service of content (e.g., video oraudio files). Thus, a request for congestion metrics (e.g., levels ofnetwork congestion, stability factors associated with the levels ofnetwork congestion, and/or predictions related to prospective levels ofnetwork congestion and/or predictions in connection with determinedstabilities/instabilities related to impending levels of networkcongestion) are generally not received or solicited in response to,based on, or as a function of, requests from an end user device or userequipment device for the supply of a service, such as streaming video,for instance. For example, a request, to a content streaming serverdevice from a content streaming client device, for service of streamingcontent (e.g., a content file) signifies that a streaming content filewill be transferred from the content streaming server device to arequesting content streaming client device in a communicationtransaction (e.g., the request for content service from the clientdevice to the server device and the fulfillment of the request by thestreaming of requested content by the server device to the requestingclient device), wherein congestion metrics that can have beencontemporaneously obtained, from and/or determined by detection engine102, by the content streaming server device (or in instances, thecontent streaming client device) independently from the request receivedfrom the content streaming client device can be used to facilitate oreffectuate communications between the content streaming server deviceand/or the content streaming client device.

As will be appreciated by those of ordinary skill, where the stream ofcontent sent from the server device to the client device is of shortduration (e.g., less than or equal to five minutes), a single suite ofcongestion metric data (e.g., determined levels a network congestion,stability factors, and/or predictions into the future related to networkcongestion and/or stability/instability of network congestion) may besufficient. However, there can be instances where streaming content cantake significantly greater durations of time to successfully complete.For example, should streaming of content take sixty minutes, multiplesuites of congestion metric data can be required and can be receivedand/or solicited from detection engine 102. Thus, detection engine 102can disseminate, as output 112, congestion metric data at periodicand/or randomly dispersed time intervals. For instance and in accordancewith an embodiment, during the streaming of a sixty minute video,detection engine 102 can dispatch, as output 112, a successive suite ofcongestion metrics (or the respective individual components thatcomprise the suite) at periodic five minute intervals. Further, inaccordance with a further additional and/or alternative embodiment forthe streaming of the aforementioned sixty minute video, detection engine102 can disseminate the group of congestion metrics (or the individualcomponents of the group of congestion metrics) at randomlyidentified/determined time intervals.

In accordance with the foregoing, it should be observed that the variousdevices (e.g., end-user client device, streaming server device, andsystem 100—the device on which detection engine 102 is operational) canreside on disparate segments of the Internet and/or the wirelesscellular network. For instance, the end-user device can be connected toa first segment of a wireless cellular network, the device on whichdetection engine 102 is operational can also be communicatively coupledto a second segment of the wireless cellular network, and/or thestreaming server device can also be communicatively coupled, via theInternet, to the wireless cellular network. In this instance, thestreaming server device, in collaboration with facilities provided bydetection engine 102 on the second segment of the wireless cellularnetwork, can assess the network congestion being experienced by theend-user client device on the first segment of the wireless cellularnetwork and can't adjust the streaming of content to the client deviceaccordingly.

As will also be appreciated by those of ordinary skill in the art, thereare additional/alternative techniques that can be used to facilitatecontent streaming/transmission. One illustrative technique of contentstreaming/transmission is adaptive bit rate. In such situations, it isnot the streaming service device that controls the bit rates of contenttransmission/streaming in response to network congestion, but rather thestreaming content is created in multiple bit rate formats; there aremultiple files for the same content, but disparate/different videoqualities.

In accordance with content transmission/streaming using adaptive bitrates, a content client operational on an end user device can beinformed about the multiple bit rate formatted versions of the contente.g., using a manifest file. The various versions of the content (invarious disparate bit rate formats) can have been cut into smallbroadcast chunks/segments, for example chunks/segments of about 2seconds to about 10 seconds duration. The content client, operating onthe end-user device, can use output from detection engine 102 to gatherinformation regarding network congestion (e.g. levels of extant networkcongestion, the stability associated with the identified levels ofnetwork congestion, and/or predictions regarding the duration over whichthe network congestion is expected to last, as well as predictions as tohow stable or unstable the network congestion is expected to be into animminent and/or defined duration of time). It should be noted in regardto the dissemination of metrics supplied and/or obtained from detectionengine 102, that such information can be dispatched individually and asa group, suite, or set of metrics. Detection engine 102 can thusdisseminate, or on request supply, the metrics on an individual basisand/or detection engine 102 can dispatch, or on request deliver, agrouping of the metrics at defined instances/intervals of time.

A client operational on an end-user device, in response to, based on, oras a function of, congestion metrics received, as output 112, fromdetection engine 102, can determine which of the various and disparatemulti-bit rate formatted content to request from the content streamingserver to satisfy a request for content. For example, if it isdetermined, by the end-user device, as a function of congestion metricsreceived from and output by detection engine 102, that networkcongestion is low, the content client executing on the end-user devicecan cause content segments formatted for the highest bit rate with thehighest video quality to be transmitted from the content server.Further, if the end-user device determines, based on the congestionmetrics or a subset, or an individual congestion metric, that aprospective duration of time is expected to be a period of high networkcongestion, the content client operational on the end-user device cancause content segments formatted for a lower bit rate and/or acommensurately lower video quality to be dispatched from the contentservice operational on a content server device.

FIG. 2 provides further illustration of a system 200 for transmittingconsecutive, continuous, and/or uninterrupted streams of networkcommunication packets between network endpoint devices, such as serverclass computing devices, laptop computer devices, tablet computerdevices, cellular telephony devices, Smartphone devices, personaldigital assistant devices, industrial and/or consumer electronicdevices, terrestrial and/or orbital communication devices, and the like.As depicted, system 200 can include load component 202 that can utilizefacilities provided by detection engine 102, processor 104, memory 106,and storage 108 to supply a congestion level metric associated with amobile wireless cellular network. In accordance with an embodimentand/or aspect, load component 202 can determine a metric (e.g., acongestion metric) associated with the level of congestion currentlyprevalent within the mobile wireless cellular network (or a sub-portionthereof comprising a first mobile wireless cellular device and a secondmobile wireless cellular device) by employing load data comprisingcell/sector load/utilization conditions received as input 110 from, forexample, operation support system devices, network probe devices, mobileswitching center devices, base station controller devices, basetransceiver devices, databases stored and/or associated with localand/or remote computing devices and/or local and/or remote data storagedevices. Load component 202 can determine the level of congestioncurrently prevalent within the mobile wireless cellular network bynoting the number of congestion events that exceed a first defined orpre-established threshold or set point and/or that surpass a seconddefined or pre-established threshold or set point, wherein first definedor pre-established threshold or set point can, for example, be relatedto a mean, median, or modal utilization mobile wireless cellular networkutilization, and the second defined or pre-established threshold or setpoint related to the duration of each of the congestion events thatexceed the first defined or pre-established threshold or set point. Thedetermined metric can thereafter be output as output 112 and thereaftercan beneficially utilized by calling or invoking applications toschedule and/or transmit continuous streams of network communicationpackets to receiving mobile wireless cellular network end point and/orend user devices.

FIG. 3 provides illustration of system 300 for transmitting orscheduling transmissions of consecutive network communication packets ina continuous uninterrupted stream from a server end point device to aplurality of client end point devices. In accordance with an embodimentthe server end point device can be a smart phone device, tablet computerdevice, laptop computer device, notebook computer device, desktopcomputer device, server class computing device(s), electronic devicesinclusive of processor(s) and memories, wired and/or wireless consumerand/or commercial electronic devices, etc. Similarly, the plurality ofclient end point devices can include consumer equipment devices, such astelevisions, digital video recorders, terrestrial and/or satelliteindustrial and/or consumer store and/or forward devices used forcontemporaneous and/or delayed broadcast or rebroadcast of content, andthe like.

As illustrated, system 300 can include stability component 302 that canoperate in collaboration with load component 202 and can becommunicatively coupled to detection engine 102, processor 104, memory106, and/or storage 108. In accordance with an embodiment, stabilitycomponent 302 can utilize the congestion metric generated or supplied byload component 202 to determine a stability factor to associate with thecongestion metric. The stability factor can be determined by stabilitycomponent 302 by using one or more statistical techniques to ascertainhow stable the level of congestion within the mobile wireless cellularnetwork has been in the immediate past. Illustrative statisticaltechniques that can be employed by stability component 302 to determinethe constancy of the level of congestion within the mobile wirelesscellular network (or portions thereof) can include determining whetheror not there is a centrality of the clustering of the distribution ofobserved congestion events (e.g., congestion events that exceed theabove noted first defined threshold or set point and/or go beyond thesecond defined threshold or set point) around an estimator, such as amean, median, or mode.

Additional and/or alternative techniques that can employed by stabilitycomponent 302 can include determining the variability of thedistribution of observed congestion events around the estimator bydetermining a variance and/or standard deviation, determining averagedeviations from the estimator, mean absolute deviations from theestimator, skewness of the distribution in relation to the center of thedistribution, and/or kurtosis of the distribution of the observedcongestion events.

The stability factor determined by stability component 302 can then beoutput, as output 112, and used by an invoking or calling application tofacilitate scheduling and/or transmission of continuous uninterruptedstreams of network communication packets directed toward end userdevices and/or user equipment devices. In using the stability factordetermined by stability component 302 invoking or calling applicationscan avoid long duration congestion events that can, at certain instancesof time, be prevalent within a mobile wireless cellular network and/orbetween one or more transmitting end point devices and one or morereceiving end point devices that can comprise the mobile wirelesscellular network.

FIG. 4 provides additional illustration of system 400 for transmittingand/or scheduling transmission of network communication packets in acontinuous, uninterrupted, and/or consecutive series between mobilewireless cellular endpoint network devices. Illustrative mobile wirelesscellular endpoint network devices can include first devices tasked withscheduling and/or transmitting a continuous, uninterrupted, and/orconsecutive series of mobile wireless cellular network communicationpackets and second devices tasked with receiving the continuous,uninterrupted, and/or consecutive series of mobile wireless cellularnetwork communication packets.

As depicted system 400 can include detection engine 102, processor 104,memory 106, storage 108, load component 202, and stability component302. Additionally, system 400 can also comprise predication component402 that can utilize communicatively coupled detection engine 102,processor 104, memory 106, storage 108, load component 202, and/orstability component 302 to generate and associate a prediction relatedto the stability factor that can have been generated by stabilitycomponent 302. The prediction generated and assigned by predictioncomponent 402 to a previously generated stability factor can provideprospective indication as to whether or not the congestion (or as thecase may be, non-congestion) and/or the level of congestion ornon-congestion is expected to last into an immediate and/or proximatedefined and definable time period. A technique that can be employed byprediction component 402 for the purposes of assigning or associating aprediction regarding the stability factor associated with the level ofcongestion can include using a probabilistic based or statistical basedapproach, for example, in connection with making an inference related tothe stability factor associated with the level of congestion. In thisinstance, prediction component 402 can make inferences that can be basedupon explicit training of classifiers or implicit training based onsystem feedback, previously persisted metrics associated with pastcongestion levels (e.g., supplied or obtained from operation supportsystem devices, mobile switching center devices, base station controllerdevices, base transceiver station devices, one or more databases and/ordata stores persisted to remote and/or local data storage devices,network probe devices, and the like). Any suitable scheme (e.g., neuralnetworks, expert systems, Bayesian belief networks, support vectormachines (SVMs), Hidden Markov Models (HMMs), fuzzy logic, data fusion,etc.) can be used by predication component 402 to provide an appropriateprediction to associate with the stability factor. Historical dataand/or extrinsic data, for example, can beneficially be used byprediction component 402 to compute a cost of making an incorrectdetermination or inference versus a benefit of making a correctdetermination or inference. Accordingly, a utility-based analysis can beemployed by prediction component 402 to provide a prediction in relationto the stability factor. Ranking and confidence measures can also bedetermined and employed by predication component 402 in connection withsuch a predictive analysis.

FIGS. 5A and 5B provide representation of a mean network utilizationthat can be encountered or experienced in a typical mobile wirelesscellular network. FIG. 5A illustrates network congestion that can occurmany times over a defined or established period of time. As will benoted on examination of FIG. 5A there are multiple instances wherenetwork utilization surpasses or exceeds a defined mean utilizationthreshold or set point (that in this illustration has been defined as50%), and there are multiple instances where network utilization peaksat 100%. Such a bursty utilization profile, as represented in FIG. 5A,can be typical in a mobile wireless cellular network and for the mostpart streaming applications (such as multimedia stream applications),for instance, are sufficiently equipped with ameliorative techniques tohandle these short duration congestion events.

FIG. 5B in contrast represents a mean network utilization that streamingapplications are not generally able to ameliorate. As will be observedupon scrutiny of FIG. 5B the level of network congestion both exceedsthe defined mean utilization threshold or set point and further peaks ata maximum utilization level of 100% for a significant duration of time.It is these long duration congestion events that most streamingapplications, for example, are not configured or adapted to handle. Fromthe perspective of such a streaming application, the ability to know inadvance of the possibility and/or the extent (predicted duration and/orstability) of such an extended all consuming congestion event can aidthese applications to better schedule and/or transmit to one or morereceiving end user devices continuous uninterrupted streams of contentencapsulated in consecutive network communication packets.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIGS. 6-8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the disclosure is not limited by theorder of acts, as some acts may occur in different orders and/orconcurrently with other acts from that shown and described herein. Forexample, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates a method 600 for scheduling transmission of streamsof transmission packets from a server device (e.g., a streaming serverdevice, such as, a smart phone, tablet computer, laptop computer,notebook computer, desktop computer, server class computing devices withor without wired and/or wireless capabilities, electronic devicesinclusive of processors and/or memories, consumer and/or commercialwired/wireless devices, industrial wired and/or wireless equipment,avionics/aviation components) to an end user device or user equipmentdevice, such as a tablet computer and/or a smart phone. Method 600 cancommence at 602 where load data comprising cell/sector load/utilizationconditions can be received from, for example, mobile wireless cellularnetwork devices that can comprise one or more of an operations supportsystem device, network probe device, mobile switching center device,base station controller device, base transceiver station device, and/orone or more relevant remote and/or local databases or data storespersisted to database server device(s). At 604, a level of congestionextant in the mobile wireless cellular network can be determined. Thelevel of congestion can be measured, for instance, by observing aquantum of congestion events that exceed a first defined orpredetermined threshold or first set point (e.g., a mean utilizationthreshold as illustrated in FIG. 5) and that surpass a second defined ordefinable threshold or second set point related, for example, to aperiod or duration of time, such as one millisecond, one second, oneminute, etc. In this manner, long (and/or excessively long) durationcongestion events that surpass, for example a mean, modal, and/or medianutilization, can be noted, and thereafter can be beneficially utilizedby invoking or calling applications to schedule packet transmissionsthat can involve the transmission of continuous series or successivesequences of packets containing content that is required to be receivedby an end user device as an uninterrupted continuous sequence ofconsecutive communication packets. At 606, in response to, based on, oras a function of, the determined metric regarding the level ofcongestion, or more specifically, the quantum of long durationcongestion events that have exceeded or surpassed a fixed or establishedutilization threshold and/or that extend beyond a predetermined,identified, or distinct time period or time horizon assessed to haveoccurred in the mobile wireless cellular network, an applicationutilizing the disclosed and described network load API can scheduletransmission of packets in order to avoid or obviate these long durationcongestion events.

FIG. 7 illustrates a further method 700 for scheduling transmissions ofconsecutive transmission packets in a continuous uninterrupted streamfrom a server device, such as a smart phone, tablet computer, laptopcomputer, notebook computer, desktop computer, server class computingdevices, electronic devices that include processors and/or memories,wired and/or wireless consumer and/or commercial devices, industrialequipment, avionics/aviation components, and the like, to an end userdevice or user equipment device, such as a small form factor device suchas a tablet computer and/or a smart phone.

Method 700 can commence at 702 where a measured level of congestion canbe determined or ascertained as a function of received load data relatedto cell/sector load/utilization conditions prevalent in a mobilewireless cellular network can be gleaned or obtained from one or moremobile wireless cellular network devices, such as operation supportsystem devices, mobile switching center devices, base station controllerdevices, base transceiver devices, network probe devices, and/ordatabases persisted to, or stored in, remote and/or local databasedevices or database storage devices. At 704 based on, as a function of,or in response to, determining the measured level of congestion metricassociated with a mobile wireless cellular network (e.g., an observationregarding a number of network traffic occurrences that both transcend anestablished or defined threshold pertaining to a mean, median, and/ormodal mobile wireless cellular network utilization and that surpass aset point related to a defined duration of time) a stability factorassociated with the measured level of congestion metric can bedetermined. The stability factor can be determined by using one or morestatistical methodologies to ascertain how stable the level ofcongestion within the mobile wireless cellular network has been in thepast. Such statistical methodologies can include, for example,determining whether or not there is a perceptible central clustering ofthe distribution of measured level of congestion around an estimator,such as a mean, median, or mode and thereafter determining thevariability of the distribution of measured levels of congestion aroundthe estimator. For instance, in order to determine the variability ofthe distribution around the estimator, variance and/or standarddistribution analyses can be carried out.

Additional and/or alternative techniques to determine the centrality ofthe distribution of measured levels of congestion around the estimatorcan also include determining average deviations from the estimator, meanabsolute deviations from the estimator, skewness of the distribution inrelation to the center of the distribution, and/or the kurtosis of thedistribution of measured levels of congestion (e.g., the relativepeakedness or flatness of the distribution relative to the estimator).

Thereafter, at 706, as a function of, and/or based on, the stabilityfactor determined at 704, an invoking or calling application utilizingthe stability factor associated with the measured level of congestionmetric (and/or in conjunction with the measured level of congestionmetric) and generated by the disclosed and described network load APIcan transmit continuous uninterrupted steams of communication packets toend user devices and/or user equipment devices while avoiding any longduration congestion events that can be prevalent within the mobilewireless cellular network.

FIG. 8 illustrates another method 800 for scheduling transmission ofcommunication packets in an uninterrupted, continuous, and/orconsecutive stream between two or more endpoint network devices, such asserver devices (e.g., enterprise or industrial class computing devices,and the like) and/or user equipment devices (e.g., consumer equipmentdevices such as televisions, digital video recorders, terrestrial andsatellite industrial store and/or forward devices used forcontemporaneous broadcast of content, delayed broadcast of content,and/or for subsequent and/or delayed rebroadcast of content, etc.).Method 800 can commence at 802 where, as a function of load data relatedto cell/sector load/utilization condition data received from mobilewireless cellular network devices that can include, network probedevices, operations support system devices, mobile switching centerdevices, base station controller devices, base transceiver devices,and/or databases stored in or on remote and/or local database devices ordatabase storage devices, a level of network congestion currently extantbetween the two or more endpoint network devices can be determined. Thelevel of network congestion extant between the two or more endpointnetwork devices can be evaluated based on, or as a function of, anenumeration of congestion events that can have occurred during a definedor identifiable duration of time (e.g., nanosecond, millisecond, second,minute, quarter hour, half hour, one hour, between two defined and/ordeterminable points in time, etc.) that exceed a first threshold orfirst set point that relates to a mean, median, and/or modal mobilewireless cellular network (or sub-portions thereof—cells or cell sectorscontrolled by one or more base stations) utilization and/or thatsurpasses a second threshold or second set point that pertains to theduration or length of the congestion event within the defined oridentifiable duration of time. Based on, or as a function of, theforegoing level of network congestion a stability factor associated withthe level of network congestion can be assessed at 804. As notedearlier, the stability factor associated with the level of networkcongestion extant between the two or more endpoint network device can beobtained by using statistical methodologies, such as determining whetheror not there is an observable clustering of the distribution ofcongestion events around an estimator, such as a mean, median, or modalcongestion event, and/or thereafter determining a variance in relationto the distribution of congestion events from the mean, median, or modalcongestion event. Additional and/or alternative non-limiting statisticaltechniques that can also be beneficially utilized in this regard caninclude: obtaining an average deviation from the estimator, identifyinga mean absolute deviation from the estimator, evaluating skewness of thedistribution in relation to the estimator, and/or assessing a kurtosisassociated with the distribution of congestion events relative to theestimator.

At 806, a prediction related to the stability factor can be carried outwherein the prediction regarding the stability factor can be associatedwith the stability factor. In this regard, the prediction provides anindication as to whether or not the congestion or the non-congestionand/or the level of congestion or level of non-congestion is expected tolast into a prospective defined or determinable near future time period.One technique for assigning or associating a prediction regarding thestability factor associated with the level of congestion can includeemploying a probabilistic based or statistical based approach, forexample, in connection with making an inference related to the stabilityfactor associated with the level of congestion. In this instance,inferences can be based in part upon explicit training of classifiers orimplicit training based at least in part upon system feedback,previously persisted metrics associated with congestion levels (e.g.,supplied or obtained from operation support system devices, mobileswitching center devices, network probe devices, base station controllerdevices, base transceiver station devices, one or more databases and/ordata stores persisted to remote and/or local data storage devices, andthe like). Any suitable scheme (e.g., neural networks, expert systems,Bayesian belief networks, support vector machines (SVMs), Hidden MarkovModels (HMMs), fuzzy logic, data fusion, etc.) can be used to provide anappropriate prediction to associate with the stability factor.Historical data and/or extrinsic data, for example, can beneficially beused to compute a cost of making an incorrect determination or inferenceversus a benefit of making a correct determination or inference.Accordingly, a utility-based analysis can be employed to provide aprediction in relation to the stability factor. Ranking and confidencemeasures can also be calculated and employed in connection with such apredictive analysis.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the disclosedsubject matter described herein. Generally, wireless network platform910 can include components, e.g., nodes, gateways, interfaces, servers,or disparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included intelecommunications carrier networks, and can be considered carrier-sidecomponents as discussed elsewhere herein. Mobile network platform 910includes CS gateway node(s) 912 which can interface CS traffic receivedfrom legacy networks like telephony network(s) 940 (e.g., publicswitched telephone network (PSTN), or public land mobile network (PLMN))or a signaling system #7 (SS7) network 970. Circuit switched gatewaynode(s) 912 can authorize and authenticate traffic (e.g., voice) arisingfrom such networks. Additionally, CS gateway node(s) 912 can accessmobility, or roaming, data generated through SS7 network 970; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Moreover, CS gateway node(s) 912interfaces CS-based traffic and signaling and PS gateway node(s) 918. Asan example, in a 3GPP UMTS network, CS gateway node(s) 912 can berealized at least in part in gateway GPRS support node(s) (GGSN). Itshould be appreciated that functionality and specific operation of CSgateway node(s) 912, PS gateway node(s) 918, and serving node(s) 916, isprovided and dictated by radio technology(ies) utilized by mobilenetwork platform 910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 960 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offloadradio access network resources in order to enhance subscriber serviceexperience within a home or business environment by way of UE 975.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It should be appreciatedthat server(s) 914 can include a content manager 915, which operates insubstantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 960, or SS7 network 970. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory, by way of illustration, and not limitation, volatilememory 1020 (see below), non-volatile memory 1022 (see below), diskstorage 1024 (see below), and memory storage 1046 (see below). Further,nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, netbookcomputers, . . . ), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of thehardware of system 100, includes a processing unit 1014, a system memory1016, and a system bus 1018. System bus 1018 couples system componentsincluding, but not limited to, system memory 1016 to processing unit1014. Processing unit 1014 can be any of various available processors.Dual microprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. For the avoidance of doubt, the term“computer-readable storage device” is used and defined herein to excludetransitory media. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, mobile device 102 and/or portabledevice 104 can include a user interface embodied in a touch sensitivedisplay panel allowing a user to interact with computer 1012. Inputdevices 1036 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus (USB), an infrared port, a Bluetoothport, an IP port, or a logical port associated with a wireless service,etc. Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit-switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” and the like, areutilized interchangeably in the subject application, and refer to awireless network component or appliance that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream to and from a set of subscriber stations or providerenabled devices. Data and signaling streams can include packetized orframe-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: based on a first delayexperienced by a first communication packet sent by network equipmentcomprising a processor, determining, by the network equipment, apredictive indicator of a second delay that is expected to beexperienced by a second communication packet sent by the networkequipment, wherein the determining comprises determining the predictiveindicator based on a statistical function related to a distribution of acluster of the first delay and the second delay around an estimator,wherein the estimator is associated with a determined level ofcongestion; and facilitating, by the network equipment, a transmissionof streaming content to a user equipment based on the predictiveindicator, wherein the facilitating comprises scheduling thetransmission of the streaming content based on avoidance of the seconddelay.
 2. The method of claim 1, further comprising: prior to thedetermining of the predictive indicator, determining, by the networkequipment, a congestion metric that represents the first delayexperienced by the first communication packet sent by the networkequipment.
 3. The method of claim 1, wherein the determining of thepredictive indicator further comprises determining a variance of thecluster of the first delay and the second delay around the estimator. 4.The method of claim 3, wherein the estimator is based on a levelselected from a group of levels comprising a mean level of congestion, amedian level of congestion, and a modal level of congestion.
 5. Themethod of claim 3, wherein the network equipment is first networkequipment, and wherein the method further comprises: determining, by thefirst network equipment, the estimator based on a first mean level ofdelay expected to be experienced by the second communication packetbeing sent by the first network equipment to second network equipment,and a second mean level of delay expected to be experienced by thesecond communication packet being sent, by the first network equipmentvia the second network equipment, to third network equipment.
 6. Themethod of claim 3, wherein the network equipment is first networkequipment, and wherein the method further comprises: determining, by thefirst network equipment, the estimator based on a first median level ofdelay expected to be experienced by the second communication packetbeing sent to second network equipment, and a second median level ofdelay expected to be experienced by the second communication packetbeing sent, by the first network equipment via the second networkequipment, to third network equipment.
 7. The method of claim 3, whereinthe network equipment is first network equipment, and wherein the methodfurther comprises: determining, by the first network equipment, theestimator based on a first modal level of delay expected to beexperienced by the second communication packet being sent to secondnetwork equipment and a second modal level of delay expected to beexperienced by the second communication packet being sent, by the firstnetwork equipment via the second network equipment, to third networkequipment.
 8. The method of claim 1, wherein the determining of thepredictive indicator further comprises determining the predictiveindicator based on an enumeration of congestion events included in loaddata received from the network equipment.
 9. The method of claim 8,wherein the enumeration of the congestion events comprises events thatoccurred during a defined time interval that exceed a defined valuerelated to a duration of a congestion event during the defined timeinterval.
 10. The method of claim 8, wherein the enumeration of thecongestion events comprises events that occurred during a defined timeinterval that exceed a defined value related to a network utilizationvalue.
 11. The method of claim 1, wherein the scheduling comprisesmodifying a size of content included in the second communication packet.12. A system, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, comprising: determining a throughputindicator based on a statistical function of a cluster of a first delayand a second delay around an estimator; and transmitting streamingcontent to a user equipment based on the throughput indicator, whereinthe transmitting comprises scheduling the streaming content based onmitigation of the second delay on the streaming content, wherein thefirst delay and the second delay are respective delays experienced by acommunication packet sent to network equipment.
 13. The system of claim12, wherein the operations further comprise: prior to the determining ofthe throughput indicator, determining a congestion metric as a functionof load data received from the network equipment, wherein the congestionmetric is representative of the first delay experienced by thecommunication packet being sent to the network equipment.
 14. The systemof claim 13, wherein the network equipment is a first network equipment,and wherein the determining the throughput indicator comprises:determining the second delay experienced by the communication packetbeing sent to second network equipment via the first network equipment.15. The system of claim 13, wherein the determining of the throughputindicator comprises: determining a statistical function associated witha distribution of the cluster of the first delay and the second delayaround the estimator.
 16. The system of claim 12, wherein thedetermining of the throughput indicator comprises: determining astability factor associated with the first delay.
 17. The system ofclaim 12, wherein the determining of the throughput indicator comprises:determining a statistical function associated with a distribution of thecluster of the first delay and the second delay around the estimator.18. The system of claim 12, wherein the determining of the throughputindicator comprises: enumerating a number of congestion eventscomprising load data that exceeds a threshold load.
 19. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor, facilitate performance of operations,comprising: determining a predictive throughput indicator based on astatistical function associated with a distribution of a cluster of afirst delay and a second delay around an estimator, wherein the firstdelay and the second delay are respective delays experienced by acommunication packet; and scheduling a transmission of streaming contentto a device via first network equipment or via second network equipmentbased on the predictive throughput indicator, wherein the scheduling isbased on mitigation of a third delay during the transmission of thestreaming content.
 20. The non-transitory machine-readable storagemedium of claim 19, wherein the first delay is experienced based on thecommunication packet being sent to the first network equipment, andwherein the second delay is experienced based on the communicationpacket being sent to the second network equipment via the first networkequipment.